Summary

• What changed? - This branch adds terminal-UX/result-summary improvements across user-facing Nova workflows: Invoke-NovaBuild, Test-NovaBuild, New-NovaModulePackage, Publish-NovaModule, Update-NovaModuleTool, Update-NovaModuleVersion, Set-NovaUpdateNotificationPreference, Install-NovaCli, Invoke-NovaAgenticCopilotScaffold, and Invoke-NovaCli.
• It also adds a dedicated PlatyPS help topic for Invoke-NovaCli, updates related command help, and updates CHANGELOG.md plus RELEASE_NOTE.md to reflect the final behavior.
• Release impact: user-facing behavior changes are real, but project.json and .github/workflows/Publish.yml are unchanged, so branch semantics stay the same (develop prerelease flow first, main stable later).
• Why was this change needed? - To align Nova’s terminal workflows with clearer progress, preview, cancellation, and next-step guidance, especially in higher-risk publish/release/self-update paths.
• Link the issue, discussion, or follow-up work (for example Closes Feature/119 add an explicit skip test option to the package publish and release workflows #123). - No linked issue was provided.

Affected area

• nova CLI or command routing
• Public PowerShell cmdlet behavior
• Scaffolding or project.json handling
• Build, test, analyzer, coverage, or CI helper flow
• Package, raw upload, or package metadata workflow
• Publish, release, or GitHub Actions automation
• Self-update or notification preference behavior
• Contributor documentation (README.md, CONTRIBUTING.md, repository workflow docs)
• End-user docs (docs/*.html)
• Command help (docs/NovaModuleTools/en-US/*.md)
• src/resources/example/
• Dependency or manifest changes (project.json, workflow dependencies, release tooling)
• Security-sensitive change
• Documentation-only change
• Agentic Copilot Workflow + scaffold mirror + scaffold-sync guardrail test.
• Other

Review guidance

• Start with CHANGELOG.md and RELEASE_NOTE.md, then review the workflow implementations under src/private/build/, src/private/quality/, src/private/package/, src/private/release/, src/private/update/, src/private/scaffold/, and src/private/cli/.
• Primary files/folders changed: src/private/**, src/public/InvokeNovaCli.ps1, src/public/SetNovaUpdateNotificationPreference.ps1, src/public/UpdateNovaModuleTools.ps1, docs/NovaModuleTools/en-US/*.md, CHANGELOG.md, RELEASE_NOTE.md, and matching Pester suites under tests/.
• Notable caveat: most release/publish/update changes are output/preview/confirmation-path changes, so the highest-risk review points are -WhatIf, prerelease confirmation, local publish import, and CI dist-module restore behavior.

Validation

• Invoke-NovaBuild
• Test-NovaBuild
• ./scripts/build/Invoke-ScriptAnalyzerCI.ps1
• ./scripts/build/ci/Invoke-NovaModuleToolsCI.ps1
• Targeted Nova workflow validated (% nova build, % nova test, % nova merge, % nova deploy, % nova publish, % nova release, % nova update, % nova notification, or % nova init as relevant)
• Docs/example only; executable validation not needed

Validation notes:

Reviewed the actual diff against develop and checked CHANGELOG.md, RELEASE_NOTE.md, project.json,
.github/pull_request_template.md, .github/workflows/Publish.yml, README.md, CONTRIBUTING.md,
touched help files, and touched tests.

Executed targeted Pester coverage for the changed workflow surfaces:

• 15 focused workflow/public-wrapper suites: build, CLI routing/install, package, test, release,
  publish, version update, self-update, notification preference, scaffold
• tests/ArchitectureGuardrails.Tests.ps1

Result:

• 123 tests passed, 0 failed

Not run during release-summary prep:

• Invoke-NovaBuild
• Test-NovaBuild
• ScriptAnalyzer CI wrapper
• full CI wrapper
• live end-to-end publish/release smoke flow

Documentation and release follow-up

• README.md reviewed and updated if contributor workflow, architecture, CI, release, or automation changed
• CONTRIBUTING.md reviewed and updated if contribution expectations or review guidance changed
• CHANGELOG.md reviewed and updated if the change matters to users, maintainers, or contributors
• RELEASE_NOTE.md reviewed and updated if the change affects public cmdlet usage, CLI usage, configuration semantics, or migration expectations
• docs/NovaModuleTools/en-US/ help updated if a public command or CLI behavior changed
• docs/*.html updated if end-user workflows or examples changed
• src/resources/example/ reviewed and updated if the real-world project layout, package model, or upload workflow changed
• No documentation, changelog, release-note, or example updates were needed

Maintainability, compatibility, and risk

• Code Health / maintainability impact considered
• No breaking change
• Breaking change
• Security-sensitive change
• CI, workflow, or release-pipeline impact
• Dependency-review impact

Risk, rollout, or rollback notes:

Stable/prerelease semantics are unchanged: Publish.yml still treats main as the stable release branch
and develop as the prerelease branch, and project.json versioning was not changed in this diff.

Release-facing impact applies to both channels once shipped, but this branch will reach users through
the develop preview flow first. The unreleased CHANGELOG.md and RELEASE_NOTE.md entries match the
observed workflow/help changes; RELEASE_NOTE.md already has real entries (no placeholder) and no
compare-link footer URLs.

Highest operational risk is in publish/release/self-update/version flows because the changes alter
WhatIf, cancellation, progress, and result-summary behavior around real release operations. The Pester
coverage is good, but it is mostly mocked workflow validation, so one manual smoke pass for:

• Publish-NovaModule -WhatIf
• Invoke-NovaRelease -WhatIf
• Update-NovaModuleTool -WhatIf
• one local publish path
  would still be prudent before cutting or promoting a release.

[!IMPORTANT]
Do not use a public pull request to disclose a vulnerability before coordinated handling.
Use the private reporting path in SECURITY.md for new security issues.